Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

2032

reference: 2-tree-1
name: 2032
tree-preservation-order: undefined
2-tpo-1
uprn
address-text
point: POINT (-0.974244 50.852482)
geometry: MULTIPOLYGON (((-0.974188 50.852476,-0.974190 50.852487,-0.974198 50.852497,-0.974210 50.852505,-0.974226 50.852510,-0.974244 50.852512,-0.974261 50.852511,-0.974277 50.852506,-0.974290 50.852498,-0.974298 50.852488,-0.974301 50.852477,-0.974299 50.852466,-0.974291 50.852456,-0.974278 50.852448,-0.974263 50.852442,-0.974245 50.852440,-0.974228 50.852442,-0.974212 50.852447,-0.974199 50.852455,-0.974191 50.852465,-0.974188 50.852476)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL